docs: add @modelcontextprotocol/fastify to middleware listings - #2516
docs: add @modelcontextprotocol/fastify to middleware listings#2516ayaangazali wants to merge 1 commit into
Conversation
|
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/core
@modelcontextprotocol/server
@modelcontextprotocol/server-legacy
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
d9adf8e to
0b0546c
Compare
…ion note The GA docs pass (modelcontextprotocol#2566) added fastify to the package listings in README.md, packages/middleware/README.md and packages/server/README.md, but the client-middleware page still names only express, hono and node when disambiguating client middleware from the framework adapters. Add fastify to that list and link the existing serving/fastify.md page. Closes modelcontextprotocol#2112.
0b0546c to
9d1c1b9
Compare
|
Rebased onto main and shrunk this to one line. The GA docs pass (#2566) already added fastify to the three package listings this PR originally touched, so those edits are gone. The only site still missing it is the client-middleware page's disambiguation note, which names express, hono and node but not fastify. That is all this PR changes now, plus the link to the existing serving/fastify.md page.
|
Fixes #2112
@modelcontextprotocol/fastifyis published on npm (private: false, currently 2.0.0-beta.4, same shape as the other three middleware packages) but it wasn't mentioned in any of the prose listings. This adds it to:README.md: the overview parenthetical, the middleware packages bullet list, and the install commands block (the three spots from the issue)packages/middleware/README.md: the packages listpackages/server/README.md: the optional framework adapters linedocs/clients/middleware.md: the "not the framework middleware packages" info note (also linked the Fastify serving page next to Express and Hono)I found the last three by grepping for listings that mention hono but not fastify, and mentioned them on the issue before starting. Wording for the new fastify bullets copies the express one (app defaults + Host header validation) since that matches what the fastify package README says it does.
Checked locally:
pnpm typecheck:all,pnpm build:all,pnpm lint:allandpnpm docs:checkall pass (the docs build catches dead links, so the new fastify.md link is covered). Also confirmed the package page exists on npm so the npmjs link in the server README doesn't 404.Docs only, so no changeset added (matching earlier docs PRs like #2426 and #2427).
small disclosure: i'm a college freshman getting started with OSS and i used claude code to help verify the sites and run the checks. the edits went through me and i double checked each spot, but if i missed a convention here i'm happy to fix it :)